Skip to content

Map Strix JSON target paths to PR changes - #195

Merged
opencode-agent[bot] merged 1 commit into
mainfrom
codex/strix-json-target-path
Jun 30, 2026
Merged

Map Strix JSON target paths to PR changes#195
opencode-agent[bot] merged 1 commit into
mainfrom
codex/strix-json-target-path

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

  • Teach the Strix PR-scope mapper to extract JSON-style target/file/path fields from vulnerability reports.
  • Add a regression case for a JSON target pointing at frontend/src/components/CalendarLayout.tsx.

Verification

  • STRIX_TEST_CASE_FILTER=pr-critical-changed-json-target bash scripts/ci/test_strix_quick_gate.sh
  • bash scripts/ci/test_strix_quick_gate.sh

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode model attempts did not emit a usable current-head control block, so the approval gate used deterministic current-head evidence instead of model prose.

Findings

No blocking findings.

Summary

  • Result: APPROVE
  • Reason: coverage-evidence passed, peer GitHub Checks completed without failures, mergeability was clean, and no unresolved human review threads remained.
  • Deterministic evidence: current-head changed-file evidence (scripts/ci/strix_quick_gate.sh, scripts/ci/test_strix_quick_gate.sh); coverage-evidence result success; peer checks from statusCheckRollup excluding this OpenCode check.
  • Model outcomes: primary=failed, fallback=failed, second_fallback=failed, catalog_fallback=failed.
  • Head SHA: cd9020f1c5e150b6746c28728d774b76e39515e3
  • Workflow run: 28430016262
  • Workflow attempt: 1

Deterministic fallback approval was used only after model-output instability and did not bypass coverage, failed-check, mergeability, or human-review gates.

Change Flow DAG

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["CI script (2 files)"]
  S1 --> I1["review and security gate shell path"]
  I1 --> R1["Review risk: CI script (2 files)"]
  R1 --> V1["bash -n plus Strix self-test"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: cd9020f1c5e150b6746c28728d774b76e39515e3
  • Workflow run: 28430016262
  • Workflow attempt: 1
  • Gate result: APPROVE (approval step)

Pull request overview

OpenCode model attempts did not emit a usable current-head control block, so the approval gate used deterministic current-head evidence instead of model prose.

Findings

No blocking findings.

Summary

  • Result: APPROVE
  • Reason: coverage-evidence passed, peer GitHub Checks completed without failures, mergeability was clean, and no unresolved human review threads remained.
  • Deterministic evidence: current-head changed-file evidence (scripts/ci/strix_quick_gate.sh, scripts/ci/test_strix_quick_gate.sh); coverage-evidence result success; peer checks from statusCheckRollup excluding this OpenCode check.
  • Model outcomes: primary=failed, fallback=failed, second_fallback=failed, catalog_fallback=failed.
  • Head SHA: cd9020f1c5e150b6746c28728d774b76e39515e3
  • Workflow run: 28430016262
  • Workflow attempt: 1

Deterministic fallback approval was used only after model-output instability and did not bypass coverage, failed-check, mergeability, or human-review gates.

Change Flow DAG

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["CI script (2 files)"]
  S1 --> I1["review and security gate shell path"]
  I1 --> R1["Review risk: CI script (2 files)"]
  R1 --> V1["bash -n plus Strix self-test"]
Loading

@opencode-agent
opencode-agent Bot enabled auto-merge (squash) June 30, 2026 08:24
@opencode-agent
opencode-agent Bot merged commit 9a64baa into main Jun 30, 2026
5 checks passed
seonghobae pushed a commit that referenced this pull request Sep 2, 2026
…, not unstarted

Follow-up to §5.4 next-action item 2. Cloned the repo directly and
read its own gap-baseline doc plus src/ and migrations/: the
item-delivery/response-submission HTTP gap is real, but four PRs
already address it (#165, #195, #197, #204), all in Draft state, on
top of domain/persistence code (item_delivery.rs, response.rs,
session_http.rs) that already exists. This is a large, actively
multi-agent-worked repo (60 open PRs per its own last-evaluated
snapshot) with its own detailed gap-tracking and PR-priority system,
not a repo nobody has touched.

No code written here: starting a fresh implementation would risk
duplicating or conflicting with in-flight work this session hasn't
reviewed. Recorded the correct next step -- onboard to this repo's
own review conventions with the same depth this session gave naruon
at the start, then push one of the four existing Draft PRs toward
Ready rather than opening a new one.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M4GKADWJyd8NToEAK5SH6Q
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant